chore: merge production v1.2.1 into staging - #887
Merged
Conversation
…nches--hotfix/v1.2.1--components--OcotilloAPI chore(hotfix/v1.2.1): release 1.2.1
fix(api/asset): update access from admin to editor
Contributor
Coverage✅ 79.49% total — gate is 75%. Coverage for the Python files changed in this PR
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Back-merge of the
v1.2.1hotfix intostaging, done by hand: the automatedforward-mergerun conflicted onuv.lock(run 32787068775).
staging, includingfix(api/asset): update access from admin to editor, which was only onproduction.uv.lockconflict (the editableocotilloapiversion)to
1.2.1, matching the mergedpyproject.toml;uv lock --checkis clean..release-please-manifest.staging.jsonto1.2.1so the next stagingRC versions from the new stable baseline.
Prerequisite for the 1.3.0 promotion:
v1.2.1was not instaginghistory, sorelease-please was scoping the RC against
v1.2.0.If version files conflict with in-flight staging work, accept either side —
release-please rewrites them on the next Release PR.